Skip to content

Make queryservice memory and probe settings configurable - #222

Open
addshore wants to merge 1 commit into
mainfrom
feat/queryservice-memory-settings
Open

addshore wants to merge 1 commit into
mainfrom
feat/queryservice-memory-settings

Conversation

@addshore

Copy link
Copy Markdown
Collaborator

Expose the existing JVM MaxRAM value and an optional MaxDirectMemorySize limit so environments can tune memory without changing the image. Add an optional startup probe and configurable HTTP probe timeouts to accommodate slower local startup and responses.

Preserve existing defaults: MaxRAM=2g, no explicit direct-memory limit, no startup probe, and one-second HTTP probe timeouts. All probes remain controlled by useProbes.
Leave the image write-cache configuration unchanged, as the change is more complex, even though this would also give local development some more gains, perhaps might folloup with that.

Expose the existing JVM MaxRAM value and an optional MaxDirectMemorySize limit
so environments can tune memory without changing the image.
Add an optional startup probe and configurable HTTP probe timeouts
to accommodate slower local startup and responses.

Preserve existing defaults: MaxRAM=2g, no explicit direct-memory limit, no startup probe, and one-second HTTP probe timeouts.
All probes remain controlled by useProbes.
Leave the image write-cache configuration unchanged, as the change is more complex, even though
this would also give local development some more gains, perhaps might folloup with that.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant